|
|
|
|
|
|
|
A Task queues are lists of tasks that need to be completed as part of a process. Some process owners need the ability to queue their tasks at the workgroup level. That is, instead of immediately routing tasks to an individual, tasks are routed to a workgroup queue. This way, users receive a task once they're free to work on it. Having this capability is beneficial for those environments where more than one user implements a role. |
|
|
|
|
|
|
|
|
The workshop includes quiz questions to help gauge your grasp of the material. You'll find the answers to this quiz in Appendix A, Answers. Even if you feel that you totally understand the concepts presented here, you should work through the quiz anyway. The last section includes exercises for you to work through to help reinforce your learning. |
|
|
|
|
|
|
|
|
1. What security features should you implement in your commercial or industrial applications? |
|
|
|
|
|
|
|
|
2. What are some factors to look for with regard to application sabotage? |
|
|
|
|
|
|
|
|
3. What are the general steps involved in a typical task? |
|
|
|
|
|
|
|
|
4. Why is it generally wise not to tightly couple a workgroup with a traditional department or a role with a user? |
|
|
|
|
|
|
|
|
5. Briefly explain the order sequence of roles in a workgroup. |
|
|
|
|
|
|
|
|
1. Using the code provided on the CD, design and implement a InvestmentAccountManager role class. |
|
|
|
|
|
|
|
|
2. In a series of steps, explain how you would consolidate the use of common forms between the BankTellerRole and RegularAccountManager role classes. Try to implement this strategy into the example code. |
|
|
|
|
|
|
|
|
3. Implement code in each role class that displays the start and stop times for each task in a message box. |
|
|
|
|
|